Techniques for point cloud filtering

ABSTRACT

A set of POIs of a point cloud are received at a first filter, where each POI of the set of POIs comprises one or more points. Each POI of the set of POIs is filtered. A set of neighborhood points of a POI is selected. A metric for the set of neighborhood points is computed. Based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to a second filter, to extract at least one of range or velocity information related to the target is determined. Provided the POI is accepted or modified, the POI is transmitted to a filtered point cloud; provided the POI is rejected, the POI is prevented from reaching the filtered point cloud; provided the POI is not accepted, modified, or rejected, the POI is transmitted to a second filter.

RELATED APPLICATIONS

This application claims priority from and the benefit of U.S. Provisional Patent Application No. 63/092,228 filed on Oct. 15, 2020, the entire contents of which are incorporated herein by reference in their entirety.

TECHNICAL FIELD

The present disclosure relates generally to point set or point cloud filtering techniques and, more particularly, point set or point cloud filtering techniques for use in a light detection and ranging (LiDAR) system.

BACKGROUND

Frequency-Modulated Continuous-Wave (FMCW) LiDAR systems include several possible phase impairments such as laser phase noise, circuitry phase noise, flicker noise that the driving electronics inject on a laser, drift over temperature/weather, and chirp rate offsets. FMCW LiDAR point clouds may exhibit distinct noise patterns, which may arise from incorrect peak matching leading to falsely detected points that appear in the scene even when nothing is present. For example, when an FMCW LiDAR points to a fence or a bush, a number of ghost points may appear in the scene between the LiDAR and the fence. These ghost points or noisy points, which are also classified as False Alarm (FA) points, if left unfiltered, may introduce ghost objects and cause errors in the estimated target range/velocity.

SUMMARY

The present disclosure describes various examples of point cloud filters in LiDAR systems.

In some examples, disclosed herein is a method of filtering a point cloud. The characteristic features of FA points, which distinguish the FA points from true detections, may be exploited to identify the FA points and regions. When a point cloud is passed to a filtering algorithm, referred to herein as a filter, the filter works on either a single point or multiple points, referred to as points of interest (POI), at a given time. Some points and statistics from the neighborhood of the POI may be provided to the filter to provide a context. The context may be used to make a decision on the POI to check if the characteristics of the POI are consistent with the neighborhood points. The context may include contextual data around the POI to aid the filter to make a decision on the POI, by checking POI's consistency with the neighborhood points. Different metrics may be formulated to quantify these statistics/characteristics. Multiple filters may be designed to identify FA points with characteristics that are different from the point cloud. The identified FA points are then subsequently modified or removed from the point cloud. The resulting point cloud is a filtered out version of the original point cloud without the FA points. For example, the filter may iteratively get a POI from the point cloud, select points in the neighborhood of the POI to provide a context to the filter, and calculate a metric over the POI and its neighbors and then make a decision to keep, remove, or modify the POI (e.g., based on the calculated metric).

In some examples, a method of filtering points in a point cloud is disclosed herein. A set of POIs of a point cloud are received at a first filter, where each POI of the set of POIs comprises one or more points. Each POI of the set of POIs is filtered. A set of neighborhood points of a POI is selected. A metric for the set of neighborhood points is computed. Based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to a second filter, to extract at least one of range or velocity information related to the target is determined. Provided the POI is accepted or modified, the POI is transmitted to a filtered point cloud to extract the at least one of range or velocity information related to the target; provided the POI is rejected, the POI is prevented from reaching the filtered point cloud; provided the POI is not accepted, modified, or rejected, the POI is transmitted to a second filter to determine whether to accept, modify, or reject the POI to extract the at least one of range or velocity information related to the target.

In some examples, a LiDAR system is disclosed herein. The LiDAR system comprises a processor and a memory to store instructions that, when executed by the processor, cause the system to receive, at a first filter, a set of POIs of a point cloud, where each POI of the set of POIs comprises one or more points. The system is further to filter each POI of the set of POIs. The system is to select a set of neighborhood points of a POI; compute a metric for the set of neighborhood points; and determine, based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to a second filter to extract at least one of range or velocity information related to the target. Provided the POI is accepted or modified, the system is to transmit the POI to a filtered point cloud to extract the at least one of range or velocity information related to the target; provided the POI is rejected, the system is to prevent the POI from reaching the filtered point cloud; provided the POI is not accepted, modified, or rejected, the system is to transmit the POI to a second filter to determine whether to accept, modify, or reject the POI to extract the at least one of range or velocity information related to the target.

In some examples, a LiDAR system is disclosed herein. The LiDAR system comprises an optical source to transmit a portion of a light signal towards a target, an optical receiver to receive a return beam from the target based on the light signal, a circuitry, and a memory to store instructions that, when executed by the processor, cause the system to receive, at a first filter, a set of POIs of a point cloud, where each POI of the set of POIs comprises one or more points. The system is further to filter each POI of the set of POIs. The system is to select a set of neighborhood points of a POI; compute a metric for the set of neighborhood points; and determine, based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to a second filter to extract at least one of range or velocity information related to the target. Provided the POI is accepted or modified, the system is to transmit the POI to a filtered point cloud to extract the at least one of range or velocity information related to the target; provided the POI is rejected, the system is to prevent the POI from reaching the filtered point cloud; provided the POI is not accepted, modified, or rejected, the system is to transmit the POI to a second filter to determine whether to accept, modify, or reject the POI to extract the at least one of range or velocity information related to the target.

It should be appreciated that, although one or more embodiments in the present disclosure depict the use of point clouds, embodiments of the present invention are not limited as such and may include, but are not limited to, the use of point sets and the like.

These and other aspects of the present disclosure will be apparent from a reading of the following detailed description together with the accompanying figures, which are briefly described below. The present disclosure includes any combination of two, three, four or more features or elements set forth in this disclosure, regardless of whether such features or elements are expressly combined or otherwise recited in a specific example implementation described herein. This disclosure is intended to be read holistically such that any separable features or elements of the disclosure, in any of its aspects and examples, should be viewed as combinable unless the context of the disclosure clearly dictates otherwise.

It will therefore be appreciated that this Summary is provided merely for purposes of summarizing some examples so as to provide a basic understanding of some aspects of the disclosure without limiting or narrowing the scope or spirit of the disclosure in any way. Other examples, aspects, and advantages will become apparent from the following detailed description taken in conjunction with the accompanying figures which illustrate the principles of the described examples.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of various examples, reference is now made to the following detailed description taken in connection with the accompanying drawings in which like identifiers correspond to like elements:

FIG. 1A is a block diagram illustrating an example LiDAR system according to embodiments of the present disclosure.

FIG. 1B is a block diagram illustrating an example of a point cloud filtering module of a LiDAR system according to embodiments of the present disclosure.

FIG. 2 is a time-frequency diagram illustrating an example of FMCW LIDAR waveforms according to embodiments of the present disclosure.

FIG. 3A is a block diagram illustrating an example of a point cloud filter according to embodiments of the present disclosure.

FIG. 3B is a block diagram illustrating an example of a filter core of a point cloud filter according to embodiments of the present disclosure.

FIG. 4A is a block diagram illustrating an example of a filter core according to embodiments of the present disclosure.

FIG. 4B is a block diagram illustrating another example of a filter core according to embodiments of the present disclosure.

FIG. 5A is a block diagram illustrating yet another example of a filter core, according to embodiments of the present disclosure.

FIG. 5B is a block diagram illustrating still another example of a filter core, according to embodiments of the present disclosure.

FIG. 6 is a flow diagram illustrating an example of a process of filtering a point cloud filter according to embodiments of the present disclosure.

FIG. 7 is a block diagram illustrating an example of a process to filter a point cloud according to embodiments of the present disclosure.

DETAILED DESCRIPTION

Various embodiments and aspects of the disclosures will be described with reference to details discussed below, and the accompanying drawings will illustrate the various embodiments. The following description and drawings are illustrative of the disclosure and are not to be construed as limiting the disclosure. Numerous specific details are described to provide a thorough understanding of various embodiments of the present disclosure. However, in certain instances, well-known or conventional details are not described in order to provide a concise discussion of embodiments of the present disclosures.

The described LiDAR systems herein may be implemented in any sensing market, such as, but not limited to, transportation, manufacturing, metrology, medical, virtual reality, augmented reality, and security systems. According to some embodiments, the described LiDAR system may be implemented as part of a front-end of frequency modulated continuous-wave (FMCW) device that assists with spatial awareness for automated driver assist systems, or self-driving vehicles.

FIG. 1A illustrates a LiDAR system 100 according to example implementations of the present disclosure. The LiDAR system 100 includes one or more of each of a number of components, but may include fewer or additional components than shown in FIG. 1 . According to some embodiments, one or more of the components described herein with respect to LiDAR system 100 can be implemented on a photonics chip. The optical circuits 101 may include a combination of active optical components and passive optical components. Active optical components may generate, amplify, and/or detect optical signals and the like. In some examples, the active optical component includes optical beams at different wavelengths, and includes one or more optical amplifiers, one or more optical detectors, or the like.

Free space optics 115 may include one or more optical waveguides to carry optical signals, and route and manipulate optical signals to appropriate input/output ports of the active optical circuit. The free space optics 115 may also include one or more optical components such as taps, wavelength division multiplexers (WDM), splitters/combiners, polarization beam splitters (PBS), collimators, couplers or the like. In some examples, the free space optics 115 may include components to transform the polarization state and direct received polarized light to optical detectors using a PBS, for example. The free space optics 115 may further include a diffractive element to deflect optical beams having different frequencies at different angles.

In some examples, the LiDAR system 100 includes an optical scanner 102 that includes one or more scanning mirrors that are rotatable along an axis (e.g., a slow-moving-axis) that is orthogonal or substantially orthogonal to the fast-moving-axis of the diffractive element to steer optical signals to scan a target environment according to a scanning pattern. For instance, the scanning mirrors may be rotatable by one or more galvanometers. Objects in the target environment may scatter an incident light into a return optical beam or a target return signal. The optical scanner 102 also collects the return optical beam or the target return signal, which may be returned to the passive optical circuit component of the optical circuits 101. For example, the return optical beam may be directed to an optical detector by a polarization beam splitter. In addition to the mirrors and galvanometers, the optical scanner 102 may include components such as a quarter-wave plate, lens, anti-reflective coating window or the like.

To control and support the optical circuits 101 and optical scanner 102, the LiDAR system 100 includes LiDAR control systems 110. The LiDAR control systems 110 may include a processing device for the LiDAR system 100. In some examples, the processing device may be one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processing device may be complex instruction set computing (CISC) microprocessor, reduced instruction set computer (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like.

In some examples, the LiDAR control systems 110 may include a signal processing unit 112 such as a digital signal processor (DSP). The LiDAR control systems 110 are configured to output digital control signals to control optical drivers 103. In some examples, the digital control signals may be converted to analog signals through signal conversion unit 106. For example, the signal conversion unit 106 may include a digital-to-analog converter. The optical drivers 103 may then provide drive signals to active optical components of optical circuits 101 to drive optical sources such as lasers and amplifiers. In some examples, several optical drivers 103 and signal conversion units 106 may be provided to drive multiple optical sources.

The LiDAR control systems 110 are also configured to output digital control signals for the optical scanner 102. A motion control system 105 may control the galvanometers of the optical scanner 102 based on control signals received from the LIDAR control systems 110. For example, a digital-to-analog converter may convert coordinate routing information from the LiDAR control systems 110 to signals interpretable by the galvanometers in the optical scanner 102. In some examples, a motion control system 105 may also return information to the LiDAR control systems 110 about the position or operation of components of the optical scanner 102. For example, an analog-to-digital converter may in turn convert information about the galvanometers' position to a signal interpretable by the LIDAR control systems 110.

The LiDAR control systems 110 are further configured to analyze incoming digital signals. In this regard, the LiDAR system 100 includes optical receivers 104 to measure one or more beams received by optical circuits 101. For example, a reference beam receiver may measure the amplitude of a reference beam from the active optical component, and an analog-to-digital converter converts signals from the reference receiver to signals interpretable by the LiDAR control systems 110. Target receivers measure the optical signal that carries information about the range and velocity of a target in the form of a beat frequency, modulated optical signal. The reflected beam may be mixed with a second signal from a local oscillator. The optical receivers 104 may include a high-speed analog-to-digital converter to convert signals from the target receiver to signals interpretable by the LiDAR control systems 110. In some examples, the signals from the optical receivers 104 may be subject to signal conditioning by signal conditioning unit 107 prior to receipt by the LiDAR control systems 110. For example, the signals from the optical receivers 104 may be provided to an operational amplifier for amplification of the received signals and the amplified signals may be provided to the LIDAR control systems 110.

In some applications, the LiDAR system 100 may additionally include one or more imaging devices 108 configured to capture images of the environment, a global positioning system 109 configured to provide a geographic location of the system, or other sensor inputs. The LiDAR system 100 may also include an image processing system 114. The image processing system 114 can be configured to receive the images and geographic location, and send the images and location or information related thereto to the LiDAR control systems 110 or other systems connected to the LIDAR system 100.

In operation according to some examples, the LiDAR system 100 is configured to use nondegenerate optical sources to simultaneously measure range and velocity across two dimensions. This capability allows for real-time, long range measurements of range, velocity, azimuth, and elevation of the surrounding environment.

In some examples, the scanning process begins with the optical drivers 103 and LiDAR control systems 110. The LiDAR control systems 110 instruct the optical drivers 103 to independently modulate one or more optical beams, and these modulated signals propagate through the passive optical circuit to the collimator. The collimator directs the light at the optical scanning system that scans the environment over a preprogrammed pattern defined by the motion control system 105. The optical circuits 101 may also include a polarization wave plate (PWP) to transform the polarization of the light as it leaves the optical circuits 101. In some examples, the polarization wave plate may be a quarter-wave plate or a half-wave plate. A portion of the polarized light may also be reflected back to the optical circuits 101. For example, lensing or collimating systems used in LIDAR system 100 may have natural reflective properties or a reflective coating to reflect a portion of the light back to the optical circuits 101.

Optical signals reflected back from the environment pass through the optical circuits 101 to the receivers. Because the polarization of the light has been transformed, it may be reflected by a polarization beam splitter along with the portion of polarized light that was reflected back to the optical circuits 101. Accordingly, rather than returning to the same fiber or waveguide as an optical source, the reflected light is reflected to separate optical receivers. These signals interfere with one another and generate a combined signal. Each beam signal that returns from the target produces a time-shifted waveform. The temporal phase difference between the two waveforms generates a beat frequency measured on the optical receivers (photodetectors). The combined signal can then be reflected to the optical receivers 104.

The analog signals from the optical receivers 104 are converted to digital signals using ADCs. The digital signals are then sent to the LiDAR control systems 110. A signal processing unit 112 may then receive the digital signals and interpret them. In some embodiments, the signal processing unit 112 also receives position data from the motion control system 105 and galvanometers (not shown) as well as image data from the image processing system 114. The signal processing unit 112 can then generate a 3D point cloud with information about range and velocity of points in the environment as the optical scanner 102 scans additional points. The signal processing unit 112 can also overlay a 3D point cloud data with the image data to determine velocity and distance of objects in the surrounding area. The system also processes the satellite-based navigation location data to provide a precise global location.

FIG. 1B is a block diagram 100 b illustrating an example of a point cloud filtering module 140 in a LiDAR system according to embodiments of the present disclosure. The signal processing unit 112 may include the point cloud filtering module 140. It should be noted that, although the point cloud filtering module is depicted as residing within the signal processing unit 112, embodiments of the present disclosure are not limited as such. For instance, in one embodiment, the point cloud filtering module 140 can reside in computer memory (e.g., RAM, ROM, flash memory, and the like) within system 100 (e.g., Lidar control system 110).

With reference to FIG. 1B, the point cloud filtering module 140 includes the functionality to select neighborhood data points from a set of points, compute metrics, and make determinations concerning the acceptance, modification, removal and/or transmission of points to a point set or point cloud using one or more filters.

For instance, the point cloud filtering module 140 can include a filter 121. In some scenarios, the point cloud filtering module 140 may receive (e.g., acquire, obtain, generate or the like), at the filter 121, a set of POIs from a point cloud, where each POI of the set of POIs includes one or more points. The filter 121 includes the functionality to filter a POI of a given set of POIs provided by a particular point cloud.

As depicted in FIG. 1B, the filter 121 may include a neighborhood context module 122, a metric calculation module 123 and a decision module 124. The neighborhood context module 122 includes the functionality to select a set of neighborhood points of a POI. The metric calculation module 123 includes the functionality to compute one or more metrics for a given set of neighborhood points.

The decision module 124 includes the functionality to determine, based on a particular metric, whether to, among other things, accept the POI, modify the POI, reject the POI, or transmit the POI to the subsequent filter (not shown). In some scenarios, provided a POI is accepted or modified at a particular filter module, the decision module 124 includes the functionality to transmit a POI to another point cloud. In some scenarios, provided a POI is rejected at a particular filter, the decision module 124 can be configured to prevent the POI from reaching a particular point cloud, for example, an output point cloud.

In some scenarios, provided a POI is not accepted, modified, or rejected at a particular filter, the decision module 124 can be configured to transmit the POI to the subsequent filter module to determine whether to accept, modify, or reject the POI.

FIG. 2 is a time-frequency diagram 200 of an FMCW scanning signal 101 b that can be used by a LiDAR system, such as system 100, to scan a target environment according to some embodiments. In one example, the scanning waveform 201, labeled as f_(FM)(t), is a sawtooth waveform (sawtooth “chirp”) with a chirp bandwidth Δf_(C) and a chirp period T_(C). The slope of the sawtooth is given as k=(Δf_(C)/T_(C)). FIG. 2 also depicts target return signal 202 according to some embodiments. Target return signal 202, labeled as f_(FM)(t−Δt), is a time-delayed version of the scanning signal 201, where Δt is the round trip time to and from a target illuminated by scanning signal 201. The round trip time is given as Δt=2R/v, where R is the target range and v is the velocity of the optical beam, which is the speed of light c. The target range, R, can therefore be calculated as R=c(Δt/2). When the return signal 202 is optically mixed with the scanning signal, a range dependent difference frequency (“beat frequency”) Δf_(R)(t) is generated. The beat frequency Δf_(R)(t) is linearly related to the time delay Δt by the slope of the sawtooth k. That is, Δf_(R)(t)=kΔt. Since the target range R is proportional to Δt, the target range R can be calculated as R=(c/2)(Δf_(R)(t)/k). That is, the range R is linearly related to the beat frequency Δf_(R)(t). The beat frequency Δf_(R)(t) can be generated, for example, as an analog signal in optical receivers 104 of system 100. The beat frequency can then be digitized by an analog-to-digital converter (ADC), for example, in a signal conditioning unit such as signal conditioning unit 107 in LIDAR system 100. The digitized beat frequency signal can then be digitally processed, for example, in a signal processing unit, such as signal processing unit 112 in system 100. It should be noted that the target return signal 202 will, in general, also include a frequency offset (Doppler shift) if the target has a velocity relative to the LIDAR system 100. The Doppler shift can be determined separately, and used to correct the frequency of the return signal, so the Doppler shift is not shown in FIG. 2 for simplicity and ease of explanation. It should also be noted that the sampling frequency of the ADC will determine the highest beat frequency that can be processed by the system without aliasing. In general, the highest frequency that can be processed is one-half of the sampling frequency (i.e., the “Nyquist limit”). In one example, and without limitation, if the sampling frequency of the ADC is 1 gigahertz, then the highest beat frequency that can be processed without aliasing (Δf_(Rmax)) is 500 megahertz. This limit in turn determines the maximum range of the system as R_(max)=(c/2)(Δf_(Rmax)/k) which can be adjusted by changing the chirp slope k. In one example, while the data samples from the ADC may be continuous, the subsequent digital processing described below may be partitioned into “time segments” that can be associated with some periodicity in the LIDAR system 100. In one example, and without limitation, a time segment might correspond to a predetermined number of chirp periods T, or a number of full rotations in azimuth by the optical scanner.

FIG. 3A is a block diagram that depicts system 300 a which includes the use of a point cloud filter (e.g., point cloud filter 310) according to embodiments of the present disclosure. In some scenarios, a point cloud (e.g., 311) is a set of data points (or points) in the scene collected using one or more components of a light scanning system (e.g., LiDAR system 100). It should be noted that the terms “data point” and “point” are interchangeably used in the present disclosure.

Each point has a set of coordinates, e.g., (X, Y, Z) and/or (Range, Azimuth, Elevation), which can be used by LiDAR system 100 to determine a point's location in the scene relative to the position of one or more sensors used by LiDAR system 100. Additional attributes such as velocity, intensity, reflectivity, time recorded, metadata and the like may also be calculated for a particular point. True detection (TD) points are points in the scene that represent an object or segment of the scene such as ground, foliage, etc. False alarm (FA) points are untrue detection points, e.g., ghost points or noisy points, in the scene. FA points cannot be associated with any object or segment of the scene.

In some scenarios, point clouds (e.g., FMCW LiDAR point clouds) exhibit distinct noise patterns which primarily arise from incorrect peak matching leading to FA points that appear in the scene even when nothing is present. For example, when an FMCW LiDAR system scans points corresponding to a fence or a bush, a number of FA points, e.g., ghost points, may appear in the scene between the LiDAR system and the fence. The FA points have characteristic features which distinguish them from True Detection (TD) points. As described in greater detail herein, embodiments of the present disclosure can exploit these distinguishing features to identify these points and regions, and then subsequently modify or remove them from the point cloud while leaving the TD points untouched. The resulting point cloud (e.g., filtered point cloud 319) is a filtered out version of the original point cloud (e.g., point cloud 311) without the FA points.

As described herein, the point cloud filtering performed by the embodiments can remove points from a point cloud which do not satisfy a predetermined threshold for a metric. For example, a filter may refer to a filtering technique or algorithm which processes a point cloud and outputs a filtered point cloud. In some embodiments, a filter may include a process in which a point cloud is processed, e.g., points not satisfying a predetermined threshold for a metric are removed, and a filtered point cloud is outputted. The filtered point cloud produced by embodiments described herein may have some points modified and some points removed.

The filter processes, described herein according to embodiments, can process a predetermined number of points, e.g., a single point or multiple points, at a time. A predetermined number of points that the filter is configured to work on at a given time include POIs. Each POI may include one or more points. The POIs may be identified by embodiments based on a predetermined threshold, such as a velocity threshold or other types of trivial identifiers. The filters described herein can be configured to work on a POI at a time, where the POI may include a single point or multiple points.

As will be explained in greater detail, upon receipt of one or more points from a point cloud, the filters described herein can work on either a POI, a single point or multiple points, at a given time. These filters can be configured to use points and statistics from the neighborhood of the POI may be provided to the filter to provide a context. The filters can be configured to use contextual information to make decisions made for a POI and to check if the characteristics of the POI are consistent with the neighborhood points. The contextual information may include contextual data around the POI to aid the filter to make a decision on the POI, by checking POI's consistency with the neighborhood points. The embodiments described herein can be configured to use different metrics to quantify these statistics/characteristics. Multiple filters may be used to identify FA points with characteristics that are different from the point cloud. The identified FA points are then subsequently modified or removed by the described embodiments from the point cloud. The resulting point cloud is a filtered out version of the original point cloud without the FA points.

For instance, as depicted in the FIG. 3A embodiment, the point cloud 311 may be received, for example, by the filter 310. In one scenario, the filter 310 may include a point cloud fragmenter 312, a POI dispatcher 313, a filter core 315, a POI collector 316, and/or a point cloud builder 317. The point cloud 311 may be fed into the point cloud fragmenter 312, which identifies regions of the point cloud 311 that the filter 310 will be working on and creates one or more POIs that can be sent to the POI dispatcher 313. Portions of the point cloud 311 that the filter 310 does not work on are communicated or transmitted to the point cloud builder 317. The point cloud fragmenter 312 identifies the regions of the point cloud 311 that may have FA points, which in turn identifies a set of POIs for the filter to work on. The point cloud fragmenter 312 identifies the set of POIs in the regions that the filter 310 will be working on based on a predetermined threshold, for example, a velocity threshold. For example, if the filter 310 works on all points with a velocity >10 m/s, then the point cloud fragmenter 312 is configured to ignore any points with a velocity <10 m/s. The ignored points are then transmitted (e.g., communicated) to the point cloud builder 317 through the link 318 in between the point cloud fragmenter 312 and the point cloud builder 317. The points that the filter 310 has not worked on may be considered as approved by the filter 310 and are therefore present in the output point cloud 319.

In one scenario, a size of the POI may be chosen, for example, a quantity of points in the POI. Then the regions of the point cloud 311 that the filter 310 would be working on may be identified. The size of the POI and the region information may help the point cloud fragmenter 312 to fragment the point cloud 311 into the set of POIs that the filter core 315 can work on.

The POI dispatcher 313 receives the POIs from the point cloud fragmenter 312 and sends the POIs to the filter core 315, one POI at a time, for processing. In some scenarios, this dispatch mechanism may be parallelized on multiple threads/graphics processing unit (GPU) cores or field-programmable gate array (FPGA) for faster processing. The dispatch strategy chosen by embodiments can depend on how the filter Core 315 operates on the POI. In scenarios, multiple filter cores may be initialized to process multiple threads or GPU cores. In these scenarios, the POI dispatcher 313 can be configured to handle this coordination.

The filter core 315 houses one or more modules of the filter 310 which can each be configured to process the POIs, which will be discussed below. The filter core 315 may be configured to select a combination of neighborhood context strategy, metric and decision that the filter will be making. The combination may depend on the noise pattern that the filter is configured to target.

In some embodiments, the filter 310 may be configured to make decisions on the POIs including approving, modifying, rejecting, or delegating (transmitting to another filter). Once a POI is processed, the filter may determine a “filtered POI” which includes a decision made for the POI (e.g., including, but not limited to, approved, modified, rejected or delegated).

The POI collector 316 can be configured to collect the filtered POIs received from the filter core 315 and send the filtered POIs to the point cloud builder 317, for example, once all the POIs are processed.

The point cloud builder 317 can be configured to construct the point cloud 319 from all the approved points in the POIs and the bypassed POIs received from the point cloud fragmenter 312. The filtered point cloud 319 is output from the filter 310. In some scenarios, the filtered point cloud 319 may have less number of points than the input point cloud 311, as the points rejected by the filter 310 may be removed from the input point cloud 311. The point cloud builder 317 can be configured to operate in tandem with the point cloud fragmenter 312. The point cloud builder 317 is configured to receive information related to points which are not being processed by the filter core 315.

The filter 310 may also be configured to selectively operate on a smaller point group instead of waiting for the entire point cloud frame to be built to reduce overall system latency.

FIG. 3B is a block diagram illustrating an example of the filter core 315 of the point cloud filter 310 according to embodiments of the present disclosure. A filter core may be configured to target noise with specific characteristics. Multiple filter cores may be designed to tackle different potential noise patterns in the scene. The function of the filter, as described herein, may be encompassed by the filter core. It should be appreciated that the terms “filter” and “filter core” may be used interchangeably herein. In some embodiments, the filter core 315 may include a neighborhood context module 322, a metric calculation module 323 and a decision module 324. The neighborhood context module 322 is configured to select a set of neighborhood points of a POI. The metric calculation module 323 is configured to compute a metric for the set of neighborhood points. The decision module 124 is configured to determine, based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to another filter.

In some implementations, the filter core 315 may be configured to process only one POI at a time. The neighborhood context module 322 can also be configured to receive one or more neighbor POIs, statistics of the neighbor POIs, and/or the entire point cloud 311. This contextual information may be used to make a decision on the POI by checking if the characteristics are consistent with the neighborhood points. In some instances, a metric may be used by the embodiments described herein for the type of noise that the filter is processing. After processing the POI, the decision module 124 may be configured to perform one or more actions including, but not limited to, accepting, modifying, discarding, or transmitting (delegating) the POI.

FIG. 4A is a block diagram of a system 400 a that includes a filter core 415 a as used in accordance with embodiments of the present disclosure. It should be noted that the term “filter” and “filter core” may be used interchangeably in this disclosure. According to some embodiments, a filter can operate on a set of POIs in a point cloud that may be based on, for example, a combination of different selection of neighborhood data points, different metrics, and/or decisions. It should be appreciated that the examples described herein are only for illustration purposes. There may be many other embodiments of a filter core based on this disclosure.

As depicted in FIG. 4A, the filter core 415 a may include a neighborhood context module 422 a, a metric calculation module 423 a, and a decision module 424 a. The neighborhood context module 422 a may be configured to select a window of points nearby for a POI 430 a, for example, a window of data points around the POI having either the same azimuth/elevation.

The metric calculation module 423 a may be configured to compute a confidence metric based on a similarity of point properties, e.g., velocity, across the POI and the selected neighborhood data points. The filter core 415 a may be configured to check if the POI has properties that are not drastically different from the neighborhood points. For example, if the minimum, maximum, or range of velocity of the POI is within a respective predetermined threshold to the minimum, maximum, or range of the neighborhood points, then the confidence metric of the POI may be determined to be high.

The decision module 424 a may be configured to determine, based on the confidence metric, whether to accept the POI, modify the POI, reject the POI, or delegate/transmit the POI to the filter core, e.g., 515 a. The POI may be approved if the confidence metric of the POI is determined to be high. For example, when the confidence metric is within a first predetermined threshold, the POI 430 a is accepted and becomes a filtered POI 440 a. When the confidence metric is within the first predetermined threshold, but there are detected inconsistencies with the neighborhood context within a particular predetermined threshold, modifications may be made to the POI. For example, point properties such as range and/or velocity may be modified. When the confidence metric of the POI is not consistent with the neighborhood points, e.g., not consistent with a second predetermined or specified threshold, the POI is classified as an FA. The POI is to be discarded or removed or filtered out.

When a decision cannot be made, but the POI was found suspicious, then the POI may be marked as a delegated POI 450 a and transmitted (e.g., delegated) to a subsequent filter core, e.g., the filter core 515 a. The POI may be passed to the subsequent filter core 515 a. The filter core, e.g., the subsequent filter core 515 a may be configured to make a decision to accept, modify, or reject the POI. Delegating determinations in this manner can reduce the load on the subsequent filter core, e.g., the filter core 515 a, as the subsequent filter core 515 a, does not operate on the entire point cloud but only on a subset of points (i.e., the undetermined or transmitted POIs).

FIG. 4B is a block diagram of a system 400 b that includes a filter core 415 b as used in accordance with embodiments of the present disclosure. FIG. 4B provides an additional example that demonstrates the types of functions the filter can perform based on its respective hardware/software profiles described herein. For instance, the filter can be configured to perform the operations described herein constrained by compute time, power consumption, etc.

With reference to FIG. 4B, the filter core 415 b may include a neighborhood context module 422 b, a metric calculation module 423 b, and a decision module 424 b. The neighborhood context module 422 b may be configured to bypass selecting a neighborhood for a POI 430 b. The metric calculation module 423 b may be configured to check if the POI has a very low velocity (lower than a first predetermined threshold, e.g., 1 m/s) or the POI points has a very high velocity (higher than a second predetermined threshold, e.g., 100 m/s). The decision module 424 b may approve the POI if the POI has a very low velocity, the POI may become a filtered POI 440 b. The decision module 424 b may be configured to reject the POI if the POI points have a very high velocity. The decision module 424 b may be configured to delegate (transmit) any POI, e.g., with a velocity in between the first predetermined threshold and the second predetermined threshold, then the POI may become a delegated POI 450 b. Because most of the scene is usually static, any noisy dynamic points may be addressed by a subsequent filter core, e.g., 515 b.

FIG. 5A is a block diagram of a system 500 a that includes a filter core 515 a as used in accordance with embodiments of the present disclosure. For instance, with reference now to FIG. 5A, in one embodiment, the filter core 515 a may include a neighborhood context module 522 a, a metric calculation module 523 a, and a decision module 524 a. The neighborhood context module 522 a may be configured to select a 3D space neighborhood for a delegated POI 530 a (e.g., 450 a). To get the neighborhood data points in the neighborhood, a search tree (KD Tree, OctTree, or variants) may be constructed on all the POIs.

The metric calculation module 523 a may be configured to compute a variance of point properties including velocity, intensity, or range, etc. A variance of the POI properties may be computed or calculated over the 3-D space neighborhood. The POI properties may include the velocity, intensity, range, or even higher order moments such as skewness and kurtosis, etc., of the data point/POI. The variance of the POI properties (e.g., the velocity or intensity) may be calculated over the neighborhood (e.g., neighborhood data points).

The decision module 524 a may be configured to determine, based on the confidence metric, whether to accept the POI, modify the POI, reject the POI, or delegate/transmit the POI to another filter core. The variance of the data point/POI properties (e.g., the velocity or intensity) may be compared against a predetermined threshold. When the POI properties (e.g., the velocity or intensity) are lower than the predetermined threshold, the data point/POI may be accepted or approved to become a filtered POI 540 a. The filtered POI 540 a may be added to a filtered output point cloud. When the POI properties (e.g., the velocity or intensity) are not lower than the predetermined threshold, the data point/POI may be rejected. When a decision cannot be made, then the POI may be transmitted to the subsequent filter core.

Referring to FIG. 5B, the filter core 515 b may include a neighborhood context module 522 b, a metric calculation module 523 b, and a decision module 524 b. The neighborhood context module 522 b may select a window of data points in the same azimuth or elevation around a POI 530 b. The neighborhood context module 522 b may select a window of points adjacent in the scan pattern. In some embodiments, a plurality of neighborhood data points including a 2-D or 3-D space neighborhood may be selected in order to consider additional ranges of data points.

The up-chirp and down-chirp frequencies from the window of points adjacent in the scan pattern may be stored. The metric calculation module 823 may compute the metric, which may be the variance of the up-chirp or the down-chirp frequencies from the window of points. For example, the variance of the up-chirp frequencies, or the variance of the down-chirp frequencies, or the difference between the variance of the up-chirp frequencies and the variance of the down-chirp frequencies may be compared against respective predetermined thresholds.

If the variance of the up-chirp frequencies, or the variance of the down-chirp frequencies, or the difference between the variance of the up-chirp frequencies and the variance of the down-chirp frequencies is not lower than the respective predetermined threshold, the decision module 524 b may determine to reject the POI. Otherwise, the data POI may be approved to become a filtered POI 540 b or delegated/transmitted to another filter (not shown).

FIG. 6 is a flow diagram illustrating an example of a process of filtering a point cloud filter according to embodiments of the present disclosure. At step 602, an input point cloud may be received, for example, at the filter 121 (as illustrated in FIG. 1B). The input point cloud may include a plurality of points/data points.

At step 604, a set of POIs in the input point cloud may be identified or obtained. The filter (e.g., filter 121, 315, 415 a, 415 b, 515 a, 515 b) may filter each POI of the set of POIs, e.g., by iterating over each POI of the set of POIs in the input point cloud.

At step 606, at a neighborhood context module (e.g., 122, 322, 422 a, 422 b, 522 a, 522 b) of the filter, a set of neighbor POIs in a neighborhood of a POI may be selected. For example, a plurality of neighborhood data points in the neighborhood of the POI may be selected. The neighborhood context module may select points from neighbor POIs and/or from the point cloud. The neighborhood points in the neighborhood have to be selected to provide a context to a metric calculation module (e.g., 123, 323, 423 a, 423 b, 523 a, 523 b) of the filter.

In one embodiment, a window of data points around the POI in the same azimuth or elevation may be selected. The set of neighborhood data points in the same azimuth or elevation around the POI in one dimensional array may be selected.

In one embodiment, a 2-D grid neighborhood points around the POI may be selected. The set of neighborhood data points in the two dimensional grid around the POI may be selected.

In one embodiment, a 3-D space/grid neighborhood points around the POI may be selected. The set of neighborhood data points in the three dimensional space/grid around the POI may be selected. To get the neighborhood data points in the neighborhood, a search tree (k-dimensional (KD) Tree, OctTree, or variants) may be constructed on all the points. A KD Tree is a space-partitioning data structure for organizing data points in a k-dimensional space. The KD Tree is a useful data structure for several applications, such as searches involving a multidimensional search key (e.g., range searches and nearest neighbor searches) and creating point clouds. An OctTree is a tree data structure in which each internal node has exactly eight children. The OctTree is most often used to partition a three-dimensional space by recursively subdividing it into eight octants. In one embodiment, a 3-D spatio-temporal neighborhood of points from previous frames around the POI may be selected.

At step 608, at the metric calculation module (e.g., 123, 323, 423 a, 423 b, 523 a, 523 b), a metric for the set of neighborhood points is computed. Once the neighborhood of the POI is selected, the metric for the set of neighborhood points may be computed. For example, one or more properties may be computed to distinguish FA points from true detections. The metric may include one or more properties of the POI and/or the set of neighborhood points.

In one embodiment, a variance of point properties may be computed, including the variance of velocity, intensity, range, or even higher order moments such as skewness and kurtosis, etc. The point properties may include velocity, intensity, range, higher order moments such as skewness and kurtosis, etc. The metric may include the variance of point properties including the variance of velocity, intensity, range, or even higher order moments such as skewness and kurtosis, etc.

In one embodiment, a confidence (e.g., a confidence metric or value) may be determined based on a similarity of the properties including velocity, intensity, range, etc., across the POI and the selected neighborhood data points. For example, the confidence metric or value may be determined based on a similarity of velocity, intensity or range. The confidence metric may check if the POI has properties that are not drastically different from the neighborhood points. For example, if the minimum, maximum, or range of the velocity of the POI is within a respective predetermined threshold to the minimum, maximum, or the similarity of velocity with the neighborhood points, then the confidence metric of the POI may be determined to be high. The confidence metric indicates a similarity level of a point property of the POI to a point property of the neighborhood points. If a determination cannot be made, the confidence metric may be low, and more complex filters may be added to make the decision on such POIs. POIs which are clearly outliers may be rejected.

In one embodiment, absolute thresholds for the properties (e.g., velocity, intensity, and range) may be determined. For example, the POI properties including velocity, intensity, range, or higher order moments (such as skewness and kurtosis, etc.) may have predetermined thresholds. The metric may include absolute thresholds for the properties.

In one embodiment, the variance, confidence metric, difference of frequency estimate and/or intensity estimate may be determined for both up-chirp and down-chirp detections. For example, the up-chirp and/or down-chirp frequencies (as illustrated in FIG. 2 ) from a window of points adjacent in a scan pattern may be stored and the variance of the up-chirp and/or down-chirp frequencies may be computed. The metric may include the variance, confidence metric, difference of frequency estimate and/or intensity estimate for both up-chirp and down-chirp detections.

At step 610, at a decision module (e.g., 124, 324, 424 a, 424 b, 524 a, 524 b) of the filter, after the POI is processed on the metric calculation module, a decision on the POI may be made. The following options may be available, including accepting the POI, modifying the POI, discarding the POI, delegating or transmitting the POI to a subsequent filter, or scoring the POI.

When the metric or property of the POI is within a first predetermined or specified threshold, the POI is not classified as an FA. Thus, the POI is accepted to be true detections, and the POI is to be transmitted to a filtered point cloud (e.g., 319).

When the metric or property of the POI is within the first predetermined or specified threshold, but there are minor inconsistencies with the neighborhood context, minor modifications may be made to the POI. For example, the POI may be modified to smoothen the point cloud.

When the metric or property of the POI based on the metrics is not consistent with the neighborhood points, or not consistent with a second predetermined or specified threshold, the POI is classified as an FA. The POI is to be discarded or removed or filtered out. The POI is not to be present in the filtered point cloud.

When a decision cannot be made but the POI is found to be suspected to be an FA, then the POI may be marked or transmitted or delegated to a subsequent filter. The POI may be passed to the subsequent, more complicated filter. The subsequent filter may make a decision whether to accept, modify, or reject the POI.

In one embodiment, the filter may score the data point/POI with a probability that the POI is not an FA. Multiple scores of the POI from multiple filters may be reviewed, e.g., by a different algorithm, and the POI may be removed when one of the multiple scores is low.

At step 612, whether all POI in the input point cloud have been processed is determined.

At step 614, if all POI in the input point cloud have not been processed, the filter may get another POI, and repeat the foregoing steps, e.g., steps 604-610, until all POIs in the input point cloud have been processed. The steps are repeated until all the regions in the point cloud are processed.

At step 616, when all POIs in the input point cloud have been processed, the filtered point cloud may be output.

The filter may be chosen by selecting a specific combination of the neighborhood context strategy, the metric and the decision that the filter can make.

In one embodiment, the filter is designed to operate on specific regions, depending on a range or an azimuth, as different regions may have different properties and the expectation of PD/FA point and/or the predetermined thresholds of the POI properties vary region by region. Thus, the filter may vary region by region. In one embodiment, the filter may immediately operate on a portion of the point cloud instead of waiting for the entire point cloud to be built in order to reduce the overall latency.

FIG. 7 is a block diagram illustrating an example of a process to filter a point cloud according to embodiments of the present disclosure. For example, the process may be performed by a signal processing unit 112 of a LiDAR system, as illustrated in FIG. 1A-FIG. 1B. In this process, the FA points may be removed, thereby, the accuracy in the estimated target range/velocity may be improved.

At block 701, a set of POIs of a point cloud are received, e.g., at a first filter. Each POI of the set of POIs includes one or more points. In one embodiment, receiving the set of POIs further includes identifying the set of POIs of the point cloud based on a predetermined threshold.

At block 702, each POI of the set of POIs is filtered, e.g., filtering at the first filter.

At block 703, a set of neighborhood points of a POI is selected.

At block 704, a metric for the set of neighborhood points is computed.

At block 705, based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to a second filter is determined, to extract at least one of range or velocity information related to the target.

At block 706, provided the POI is accepted or modified at the first filter, the POI is transmitted to a filtered point cloud, to extract at least one of range or velocity information related to the target. The filtered point cloud may be an output point cloud. In one embodiment, the POI is accepted or modified in response to the metric satisfying a first predetermined threshold established for the metric.

At block 707, provided the POI is rejected at the first filter, the POI is prevented from reaching the filtered point cloud. In one embodiment, the POI is rejected in response to the metric not satisfying a second predetermined threshold established for the metric.

At block 708, provided the POI is not accepted, modified, or rejected at the first filter, the POI is transmitted to a second filter to determine whether to accept, modify, or reject the POI, to extract at least one of range or velocity information related to the target.

The preceding description sets forth numerous specific details such as examples of specific systems, components, methods, and so forth, in order to provide a thorough understanding of several examples in the present disclosure. It will be apparent to one skilled in the art, however, that at least some examples of the present disclosure may be practiced without these specific details. In other instances, well-known components or methods are not described in detail or are presented in block diagram form in order to avoid unnecessarily obscuring the present disclosure. Thus, the specific details set forth are merely exemplary. Particular examples may vary from these exemplary details and still be contemplated to be within the scope of the present disclosure.

Any reference throughout this specification to “one example” or “an example” means that a particular feature, structure, or characteristic described in connection with the examples are included in at least one example. Therefore, the appearances of the phrase “in one example” or “in an example” in various places throughout this specification are not necessarily all referring to the same example.

Although the operations of the methods herein are shown and described in a particular order, the order of the operations of each method may be altered so that certain operations may be performed in an inverse order or so that certain operations may be performed, at least in part, concurrently with other operations. Instructions or sub-operations of distinct operations may be performed in an intermittent or alternating manner.

The above description of illustrated implementations of the invention, including what is described in the Abstract, is not intended to be exhaustive or to limit the invention to the precise forms disclosed. While specific implementations of, and examples for, the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. The words “example” or “exemplary” are used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the words “example” or “exemplary” is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X includes A or B” is intended to mean any of the natural inclusive permutations. That is, if X includes A; X includes B; or X includes both A and B, then “X includes A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form. Furthermore, the terms “first,” “second,” “third,” “fourth,” etc. as used herein are meant as labels to distinguish among different elements and may not necessarily have an ordinal meaning according to their numerical designation. 

What is claimed is:
 1. A method of filtering points in a light detection and ranging (LiDAR) system, comprising: receiving, at a first filter, a set of points of interest (POIs) of a point cloud, wherein each POI of the set of POIs comprises one or more points; filtering each POI of the set of POIs, comprising: selecting a set of neighborhood points of a POI; computing a metric for the set of neighborhood points based on a property of the set of neighborhood points and the POI, wherein the property comprises a velocity; determining, based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to a second filter to extract at least one of range or velocity information related to the target; provided the POI is accepted or modified, transmitting the POI to a filtered point cloud to extract the at least one of range or velocity information related to the target; provided the POI is rejected at the first filter, preventing the POI from reaching the filtered point cloud; and provided the POI is not accepted, modified, or rejected at the first filter, transmitting the POI to the second filter to determine whether to accept, modify, or reject the POI to extract the at least one of range or velocity information related to the target.
 2. The method of claim 1, wherein the selecting a set of neighborhood points of a POI comprises selecting a window of data points in a same azimuth or elevation around the POI.
 3. The method of claim 1, wherein the selecting a set of neighborhood points of a POI comprises selecting a set of points in a 2-D grid neighborhood around the POI.
 4. The method of claim 1, wherein the selecting a set of neighborhood points of a POI comprises selecting a set of points in a 3-D space neighborhood around the POI.
 5. The method of claim 1, wherein the selecting a set of neighborhood points of a POI comprises selecting a set of points in a 3-D spatio-temporal neighborhood from previous frames around the POI.
 6. The method of claim 1, wherein the computing a metric for the set of neighborhood points comprises computing the metric based on a variance of a property of the set of neighborhood points and the POI, wherein the property comprises a velocity, an intensity, or a range.
 7. The method of claim 6, wherein the metric is further computed based on a higher order moment of the property of the set of neighborhood points and the POI, and wherein the higher order moment comprises a skewness or a kurtosis.
 8. The method of claim 1, wherein the computing a metric for the set of neighborhood points comprises computing the metric based on a confidence according to a similarity of a velocity, an intensity, or a range of the set of neighborhood points and the POI.
 9. The method of claim 1, wherein the computing a metric for the set of neighborhood points comprises computing the metric based on a threshold of a velocity, an intensity, or a range of the set of neighborhood points and the POI.
 10. The method of claim 1, wherein the computing a metric for the set of neighborhood points comprises computing the metric based on a variance of up-chirp frequencies or down-chirp frequencies of the set of neighborhood points and the POI.
 11. A light detection and ranging (LiDAR) system, comprising: a processor; and a memory to store instructions that, when executed by the processor, cause the system to: receive, at a first filter, a set of points of interest (POIs) of a first point cloud, wherein each POI of the set of POIs comprises one or more points; filter each POI of the set of POIs, wherein the system is to: select a set of neighborhood points of a POI; compute a metric for the set of neighborhood points based on a property of the set of neighborhood points and the POI, wherein the property comprises a velocity; determine, based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to a second filter to extract at least one of range or velocity information related to the target; provided the POI is accepted or modified, transmit the POI to a filtered point cloud to extract the at least one of range or velocity information related to the target; provided the POI is rejected, prevent the POI from reaching the filtered point cloud; and provided the POI is not accepted, modified, or rejected, transmit the POI to the second filter to determine whether to accept, modify, or reject the POI to extract the at least one of range or velocity information related to the target.
 12. The system of claim 11, wherein the system is to select a window of data points in a same azimuth or elevation around the POI.
 13. The system of claim 11, wherein the system is to select a set of points in a 2-D grid neighborhood, a 3-D space neighborhood, or a 3-D spatio-temporal neighborhood from previous frames around the POI.
 14. The system of claim 11, wherein the system is to compute the metric based on a variance of a property of the set of neighborhood points and the POI, wherein the property comprises a velocity, an intensity, or a range, or wherein the system is to compute the metric based on a variance of up-chirp frequencies or down-chirp frequencies of the set of neighborhood points and the POI.
 15. The system of claim 11, wherein the system is to compute the metric based on a confidence according to a similarity of a velocity, an intensity, or a range of the set of neighborhood points and the POI.
 16. The system of claim 11, wherein the system is to compute the metric based on a threshold of a velocity, an intensity, or a range of the set of neighborhood points and the POI.
 17. A light detection and ranging (LiDAR) system, comprising: an optical source to transmit a portion of a light signal towards a target; an optical receiver to receive a return beam from the target based on the light signal, a circuitry; and a memory to store instructions that, when executed by the circuitry, cause the system to: receive, at a first filter, a set of points of interest (POIs) of a first point cloud, wherein each POI of the set of POIs comprises one or more points; filter each POI of the set of POIs, wherein the system is to: select a set of neighborhood points of a POI; compute a metric for the set of neighborhood points based on a property of the set of neighborhood points and the POI, wherein the property comprises a velocity; determine, based on the metric, whether to accept the POI, modify the POI, reject the POI, or transmit the POI to a second filter to extract at least one of range or velocity information related to the target; provided the POI is accepted or modified, transmit the POI to a filtered point cloud to extract the at least one of range or velocity information related to the target; provided the POI is rejected, prevent the POI from reaching the filtered point cloud; provided the POI is not accepted, modified, or rejected, transmit the POI to the second filter to determine whether to accept, modify, or reject the POI to extract the at least one of range or velocity information related to the target.
 18. The system of claim 11, wherein the system is to select a window of data points in a same azimuth or elevation around the POI.
 19. The system of claim 11, wherein the system is to select a set of points in a 2-D grid neighborhood, a 3-D space neighborhood, or a 3-D spatio-temporal neighborhood from previous frames around the POI.
 20. The system of claim 11, wherein the system is to compute the metric based on a variance of a property of the set of neighborhood points and the POI, wherein the property comprises a velocity, an intensity, or a range, or wherein the system is to compute the metric based on a variance of up-chirp frequencies or down-chirp frequencies of the set of neighborhood points and the POI.
 21. The system of claim 11, wherein the system is to compute the metric based on a confidence according to a similarity of a velocity, an intensity, or a range of the set of neighborhood points and the POI.
 22. The system of claim 11, wherein the system is to compute the metric based on a threshold of a velocity, an intensity, or a range of the set of neighborhood points and the POI. 